Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1206

reference
451-tree-1
name
1206
tree-preservation-order

undefined

451-tpo-1
uprn
address-text
point
POINT (-1.006416 50.890732)
geometry
MULTIPOLYGON (((-1.006360 50.890726,-1.006362 50.890738,-1.006370 50.890748,-1.006383 50.890756,-1.006398 50.890761,-1.006416 50.890763,-1.006433 50.890761,-1.006449 50.890756,-1.006462 50.890748,-1.006470 50.890738,-1.006473 50.890727,-1.006471 50.890716,-1.006463 50.890706,-1.006451 50.890698,-1.006435 50.890693,-1.006417 50.890691,-1.006400 50.890693,-1.006384 50.890697,-1.006371 50.890705,-1.006363 50.890715,-1.006360 50.890726)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL